-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(sdk-node): move @opentelemetry/exporter-jaeger to dev dependencies #4049
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4049 +/- ##
==========================================
+ Coverage 92.56% 92.57% +0.01%
==========================================
Files 292 292
Lines 8178 8178
Branches 1692 1692
==========================================
+ Hits 7570 7571 +1
+ Misses 608 607 -1 |
As you can see in the test run a changelog entry is needed. |
Thank you @Flarna! Will add the changelog entry shortly and will update the readme as well. |
Thank you for your contribution @Vadman97, removing this exporter has been long overdue 🙂 The exporter is lazy-required in opentelemetry-js/experimental/packages/opentelemetry-sdk-node/src/TracerProviderWithEnvExporter.ts Line 76 in d3436bf
We'll also have to adapt the error message that the exporter has to be installed manually. opentelemetry-js/experimental/packages/opentelemetry-sdk-node/src/TracerProviderWithEnvExporter.ts Lines 79 to 81 in d3436bf
Previously we've gone the way of releasing a version that adds a As See also:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for working on this; this looks good as-is 🙂
For lack of a better way to do it, I'm just using the "Changes Requested" state to block this until #4068 is merged and released (as mentioned in #4049 (comment)). Once we have it released, we can merge this PR 🙂
Thanks for your help @pichlermarc , and sorry for the delay here. I'm updating the branch now to change TracerProviderWithEnvExporter.ts as you described. |
@pichlermarc - is this ready to merge now that #4068 is in? |
Yes, but we still need to cut a release first to get #4068 out 🙂 Sorry for the delay. |
@pichlermarc Seems like we can merge this PR since #4068 is out? |
f43904f
to
2c69fb1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ready to merge now that the release it out.
Adds README and CHANGELOG documentation of the change.
hey @pichlermarc , sorry to pester here - is there any estimate as to when the next version will be released to npm so that we can update our dependency on |
The release with the warning message went out last week; I'd cut another release mid-next week. |
Hey @pichlermarc , any updates here on the next release being shipped? |
## Summary References new opentelemetry dependencies with open-telemetry/opentelemetry-js#4049 merged Explicitly makes `@opentelemetry/exporter-jaeger` a dev dependency so that consumers do not reference it in their bundle. ## How did you test this change? Local e2e app using yalc published SDK. repro app is working correctly https://discord.com/channels/1026884757667188757/1138948448507404338 ![image](https://github.com/highlight/highlight/assets/1351531/31b87688-d2de-40dc-80cf-c7946b5a1eee) ## Are there any deployment considerations? Changeset included. ## Does this work require review from our design team? No
## Summary References new opentelemetry dependencies with open-telemetry/opentelemetry-js#4049 merged Explicitly makes `@opentelemetry/exporter-jaeger` a dev dependency so that consumers do not reference it in their bundle. ## How did you test this change? Local e2e app using yalc published SDK. repro app is working correctly https://discord.com/channels/1026884757667188757/1138948448507404338 ![image](https://github.com/highlight/highlight/assets/1351531/31b87688-d2de-40dc-80cf-c7946b5a1eee) ## Are there any deployment considerations? Changeset included. ## Does this work require review from our design team? No
Which problem is this PR solving?
@opentelemetry/sdk-node
depends on@opentelemetry/exporter-jaeger
despite never using it directly.This increases the number of dependencies required to install
@opentelemetry/sdk-node
even if@opentelemetry/exporter-jaeger
is not used.Fixes #3759
Short description of the changes
The change moves
@opentelemetry/exporter-jaeger
to the dev dependencies to resolve it in testsbut avoid requiring it for general usage of
@opentelemetry/sdk-node
. This is consistent with the@opentelemetry/sdk-node
documentation which statesthat exporters must be explicit dependencies.
Type of change
How Has This Been Tested?
Locally building and testing the package after running
npm install
inopentelemetry-js/experimental/packages/opentelemetry-sdk-node
.Checklist: